Release 10.1A: OpenEdge Application Server:
Administration

WSAMAN deploy

Deploys a Web service to a WSA instance.

This transfers the Web service’s WSM file to the WSA instance, which generates the Web Services Application Descriptor (WSAD), WSDL, and friendlyname.props files. Most of the properties in the friendlyname.props file are initialized from the values in the default.props file of the WSA instance you are deploying to.

Syntax

Operating system	Syntax
UNIX Windows	wsaman    -name wsainstance-name    -wsm wsm-location-on-wsaman-machine    [ -appname new-appfriendlyname ]    [ -namespace new-targetnamespace ]    [ -encoding new-encodingstyle ]    -deploy

-name wsainstance-name

The name of the WSA instance where you want to deploy the Web service.

-wsm wsm-location-on-wsaman-machine

The path of the WSM file on the WSAMAN machine.

-appname new-appfriendlyname

The new friendly name of the Web service.

Note: This value replaces the value supplied by the developer to ProxyGen.

-namespace new-targetnamespace

The new target namespace of the Web service.

Note: This value replaces the value supplied by the developer to ProxyGen.

-encoding new-encodingstyle

An integer indicating the new style/use combination of the WSDL file.

Use a value from Table B–6, which lists the WSDL style/use combinations supported.

Table B–6: Setting the SOAP format for deployment using WSAMAN 

Use this value ...	For this WSDL style/use combination ...
1	RPC/Encoded
2	RPC/Literal
3	Document/Literal

Notes

The WSM file must be locally accessible from the machine running the Progress Explorer or the WSAMAN utility; that is, located on a local drive or a mapped network drive.
Values for the appServiceName and appServiceConnectionMode properties are initialized from the WSM file, not from default.props.
When a Web service is deployed, it is initially disabled.